home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000162_icon-group-sender_Tue Dec 17 12:46:16 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id gBHJjAw05436
for icon-group-addresses; Tue, 17 Dec 2002 12:45:10 -0700 (MST)
Message-Id: <200212171945.gBHJjAw05436@baskerville.CS.Arizona.EDU>
From: aherford@yahoo.de (Alex Steinberg)
X-Newsgroups: comp.lang.icon
Subject: Re: Icon compiler
Date: 17 Dec 2002 05:35:04 -0800
X-Complaints-To: groups-abuse@google.com
To: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
"Frank J. Lhota" <NOSPAM.lhota.adarose@verizon.net> wrote in message news:<RQ6I9.266$903.163@nwrddc02.gnilink.net>...
> The Icon native code compiler is still distributed, but no longer supported.
> I experimented with making the Icon-to-C compiler work in my recent Cygwin
> port, and I discovered that the code needed a lot of tweaking.
>
> The Icon-to-C (iconc) compiler can produce very fast programs. I recall once
> using it on the Icon versions of uuencode / uudecode ("iiencode.icn" and
> "iidecode.icn" in the IPL) and ran some timing checks. The iconc versions of
> iiencode / iidecode were over 3 times as fast as the interpreted (icont /
> iconx) versions. More surprisingly, I found that the iconc programs were
> actually faster than native C uuencode / uudecode programs that I was using
> at the time!
>
> The down side is that the iconc compiler itself is sluggish and a real
> memory hog. Because of the type inference engine, iconc cannot perform
> separate compilation. My experience is that iconc is bound to fail for
> programs beyond a certain size. Also, for iconc debug support is optional,
> and a performance drag. I would not recommend compiling a program with iconc
> until it has been thoroughly tested and debugged.
>
> Also, some more recent features such as multi-threading is simply not
> supported (and not really supportable) by iconc.
>
> The iconc compiler has to interface with the local C compiler, which creates
> a real maintenance headache. It is therefore not surprising that the Icon
> Project decided to drop support for iconc.
Hello Frank,
You are talking about Your recent Cygwin port of Icon, is that port
available for the public? I have looked for some time now to such port
but without success.
thanks,
Alex